Logs and documents in test mode
View logs to research where a process failed and why.
Viewing logs and understanding the information contained in them is an important part of building, testing, and monitoring processes. Logs can help you research where a process failed and why. While the process executes in Test mode, you can watch the progression of documents through the process steps. When the test is finished, you can view the log and data files produced.
The log and data files produced during a Test mode execution are temporary! When you exit Test mode, this information is lost.
Refer to the below tabs to know more about:
- Viewing a process log in test mode
- Viewing a document log error in test mode
- Viewing a data file in test mode
- Viewing a process log in test mode
- Viewing a document log error in test mode
- Viewing a data file in test mode
There is a limited number of messages generated when you run a process in Test mode.
You can review the high-level log information for the overall process execution that ran in test mode.
-
When the process execution is completed, click the drop-down arrow next to the process name and select View Log.
The log file opens in the Base Process Log window.
-
To download the contents of the log, click Save Logs.
Depending on your browser and its download settings, you may be prompted to specify the destination path and filename. The default filename is Test_execution-executionID-yy.mm.dd.log, where executionID is the system-assigned execution ID and yyyy, mm, and dd specify the current date — for example, Test_execution-01234567-890a-bcde-f012-3456789abcde-2018.11.10.log.
-
Click Cancel.
noteYou can download the log without first opening the Base Process Log window by clicking the drop-down arrow next to the process name and selecting Download Log.
You can view the log file for a specific document that failed in test mode.
-
Click the step on the process canvas.
-
Select the failed document from the numbered list in the Documents window.
-
Refer to the Logs tab in the Test Results window.
This displays the log information for that particular step.
-
Click the Details link to learn more about the document-level error.
noteTo view the log entries for a connection in the Start step, you must view the process log.
You can view the source document and tracking information that was sent into a step.
When you are in test mode, the Start step and all Connector steps have a Connection Data tab that displays inbound or outbound documents, any connector-specific tracking information, and the View Source link to view the actual data contents.
All steps other than the Start step contain a Step Source Data tab. You can view in the Document Viewer dialog the source document that was sent into this step. This view is helpful, for example, when reviewing the source data of a map or the request data sent to an outbound connector.
-
Click the Start step or a Connector step on the process canvas.
-
Select the document from the numbered list in the Documents window.
-
Click the Connection Data tab.
-
On the Connection Data tab, click the View Source icon to open the document in the Document Viewer Dialog.
-
On the process canvas click one of the steps that is not the Start step.
-
Select the document from the numbered list in the Documents window.
-
Click the Step Source Data tab.
-
On the Step Source Data tab, click the View Source icon to open the document in the Document Viewer Dialog.
Troubleshoot test mode
When an error occurs during test execution, you may have an error message or need additional information in the process and document logs.
-
Inbound documents that were processed successfully are marked with a green check mark
and each of its process steps is highlighted in green.
-
Documents that encountered errors are marked as failed with a red X
and one of the process steps is highlighted in red.
-
If an error occurred during the execution, a dialog displays an error message.
- For more information, view the process log and/or document logs by selecting the failed document and then clicking the process step highlighted in red.
- In the log, look for the entry section marked as SEVERE, then click the Details link for more information. Depending on the error type, you may need to review the inbound data to look for bad data or exit Test mode and modify the process configuration.